Mobile handset extension to a device

ABSTRACT

Mobile operation is extended to a device. An extension interface comprises a client component within a mobile that is linked to a client component within the device. Extension of mobile operation is secured via delivery of credentials associated with the mobile to the device. Delivery of credentials is temporary and typically spans the period during which mobile operation is extended to the device. Application(s) and content(s) can be conveyed to the device for utilization therein. An emulation component that can reside at least in part on the client component within the device can emulate mobile operation. Client component within the mobile can include at least in part (i) a component that downloads drivers for communication with, and utilization of, the device to which mobile operation is extended, and (ii) a component that can scan for wireless-capable devices to extend mobile service thereto.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 14/255,910, entitled “MOBILE HANDSETEXTENSION TO A DEVICE”, filed on Apr. 17, 2014, and which is acontinuation of U.S. patent application Ser. No. 12/206,489, entitled“MOBILE HANDSET EXTENSION TO A DEVICE” filed on Sep. 8, 2008. Theentireties of the above-referenced U.S. Patent Applications areincorporated herein by reference.

TECHNICAL FIELD

The subject application relates to wireless communications and, moreparticularly, to secure extension of wireless operation and services toelectronic devices that operate outside a mobile wireless network.

BACKGROUND

Mobile wireless communication has become widely accessible in variousmarkets for a myriad applications ranging from productivity andcommerce, to remote operations in hostile or inaccessible environmentsand to entertainment. Yet, access to mobile resources requires servicecommitments like service contracts and subscriptions, which aretypically difficult to port across devices other than those for whichservice has been acquired. Moreover, as provided by wireless networkplatforms, mobile operation within contracted service exploits securityidentifiers associated with served mobile devices to ensure informationintegrity as well as secure management of communications. Furthermore,available operational resources (e.g., limited display real estate;confined keyboard space and data entry capabilities; limited font sizesthat facilitate consumption of lengthy documents) and applicationsassociated with a served mobile device like a cellular telephone canfail to be adopted widely among varied consumer segments. The latter canleave business opportunities unexploited by service providers or networkoperators. Such difficulties can hinder dramatic pervasiveness of securemobile communications and ensuing convenience.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an example system that extends operation ofa mobile handset to a device in accordance with aspects described in thesubject specification.

FIGS. 2A-2B illustrate, respectively, example mobile and deviceembodiments that facilitate mobile extension to the device, and anexample embodiment for a component that manipulates mobileapplication(s) at the device level in accordance with aspects describedherein.

FIG. 3 is a block diagram of example embodiments of a mobile and adevice to which mobile operation has been extended via an extensioninterface in accordance with aspects described herein.

FIG. 4 illustrates a block diagram of an example system that scans foravailable wireless devices to extend mobile operation thereto inaccordance with aspects described herein.

FIG. 5 is a block diagram of an example system that exploits disparatenetworks upon extension of mobile operation to a device in accordancewith aspects of the subject application.

FIG. 6 is a block diagram of an example system that exploits a mobileoperation extension interface to relay communication(s) among multipleparties in accordance with aspects disclosed in the subjectspecification.

FIG. 7 is a flowchart of an example method for extending mobile handsetoperation to a device according to aspects described in the subjectspecification.

FIG. 8 displays a flowchart of an example method for conveying contentto a device attached to a mobile handset through an extension interfaceaccording to aspects described in the subject application.

FIG. 9 is a flowchart of an example method for extending mobileoperation to available devices with wireless capability according toaspects disclosed herein.

FIG. 10 is a flowchart of an example method for utilizing an alternativeor offloading network for extension of mobile operation to a device.

FIG. 11 is a flowchart of an example method for exploiting extension ofmobile operation of a device to conduct a multi-part call according toaspects disclosed herein.

FIG. 12 is a flowchart of an example method for exploiting mobileservice through a mobile handset extension interface according toaspects described in the subject specification.

FIG. 13 is a flowchart of an example methodology for generating andemploying a device-specific application from a mobile-specificapplication when mobile operation is extended to the device according toaspects of the subject application.

FIG. 14 is a flowchart of an example methodology for manipulating anddelivering traffic through a mobile operation extension interfaceaccording to aspects of the subject application.

FIG. 15 is a block diagram of an example embodiment of a mobile thatoperates in accordance with aspects disclosed in the subjectspecification.

FIG. 16 presents a block diagram of an example embodiment of a device towhich mobile operation can be extended in accordance with aspectsdescribed herein.

DETAILED DESCRIPTION

System(s) and method(s) are provided for extension of mobile operationto a device. An extension interface comprises a client component withina mobile that is linked to a client component within a device to whichmobile operation is extended. Extension of mobile operation is securedvia communication of security credentials associated with the mobile tothe device via a link component, wired or wireless, that functionallycouples both client components in the extension interface. Extension ofsecurity credential is temporary and typically spans a time intervalduring which mobile operation is extended to the device.

In addition, application(s) and content(s) can be conveyed to the devicefor utilization thereof. An emulation component which can be at least apart of the client component that resides in the device can emulatemobile operation. Emulation can include adaptation and optimization ofreceived mobile application(s) to application(s) that optimally utilizesoperational resources of the device. Adaptation and optimization can beaccomplished through artificial intelligence or machine-learningtechniques. Moreover, a component that can be at least a part of theclient component within the device can provide add-on features (e.g.,voice and text translation, or voice-to-text and text-to-voiceconversion) to a call sustained via the mobile through the extensioninterface. Client component within the mobile can include at least aportion of a component that downloads drivers for communication with,and utilization of, the device to which mobile operation is extended.Furthermore, the client component that resides within the mobile canscan for wireless capable devices to extend mobile service thereto, andfor available wireless network within the environment of a device inorder to offload service from a first wireless network.

To the accomplishment of the foregoing and related ends, theapplication, then, comprises the features hereinafter fully described.The following description and the annexed drawings set forth in detailcertain illustrative aspects of the application. However, these aspectsare indicative of but a few of the various ways in which the principlesof the application may be employed. Other aspects, advantages and novelfeatures of the application will become apparent from the followingdetailed description of the application when considered in conjunctionwith the drawings.

The subject application is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the present application. It may be evident, however,that the present application may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the presentapplication.

As used in this application, the terms “component,” “system,”“platform,” “service,” “framework,” “interface,” “node,” and the likeare intended to refer to a computer-related entity or an entity relatedto an operational machine with one or more specific functionalities. Theentities disclosed herein can be either hardware, a combination ofhardware and software, software, or software in execution. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. Also, these components canexecute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal).

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “mobile handset,”“handset,” and similar terminology, refer to a wireless device utilizedby a subscriber or user of a wireless communication service to receiveor convey data, control, voice, video, sound, gaming, or substantiallyany data-stream or signaling-stream. The foregoing terms are utilizedinterchangeably in the subject specification and related drawings.Likewise, the terms “access point,” “base station,” “Node B,” “evolvedNode B,” “home Node B (HNB),” and the like, are utilized interchangeablyin the subject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming data, or substantially any data-stream or signaling-stream from aset of subscriber stations. Data and signaling streams can be packetizedor frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“agent,” and the like are employed interchangeably throughout thesubject specification, unless context warrants particular distinction(s)among the terms. It should be appreciated that such terms can refer tohuman entities or automated components supported through artificialintelligence (e.g., a capacity to make inferences based on complexmathematical formalisms) which can provide simulated vision, soundrecognition, and so forth.

FIG. 1 is a block diagram of an example system 100 that extendsoperation of a mobile handset 110 to a device 130. In system 100, aclient component 112 that resides within mobile 110 is functionallyconnected through a link component 115 to a client component 132 thatresides within device 130. Client components 112 and 132, and linkcomponent 115, embody an extension interface 105 that facilitatesprovision of mobile operation and information to device 130. Mobile 110can be substantially any user equipment with a SIM card. Mobile 110 isconnected through wireless uplink 137 and downlink 137 _(DL) to a radioaccess network 145 attached via link 147, which can be either wired orwireless, to a network platform 150 (e.g., a core network in cellularwireless technologies such as Third Generation Partnership Project(3GPP) Universal Mobile Telecommunication Services (UMTS)). Networkplatform 150 can be functionally connected to a set of external networkslike telephony network(s) 160, Internet Service Provider (ISP) network170, and local area network 180 (e.g., an enterprise network). Device130 can be substantially any electronic device that provides a set offunctionalities. For example, device 130 can be a personal computer(PC), an audio-visual or data projector, a television, a camera, etc.

In an aspect of the subject application, mobile operation is extendedfrom mobile 110 to device 130 via extension interface 105. Suchextension is herein termed forward mobile extension. In such scenario,functional resources of device 130 such as display interface(s), dataentry interface(s), or substantially any interface component, can act asoperational extensions of the mobile handset 110. As an example, whendevice 130 is a PC, one or more PC monitor screens and a PC keyboard canbe exploited to deliver mobile content to an end user, and to providethe end user with text entry capabilities that facilitate utilization ofcommunication applications of mobile handset 110, like short messageservice (SMS), multimedia message service (MMS), instant message (IM),email, etc. It should be appreciated that forward mobile extension canthus facilitate a mobile office, by providing connectivity (e.g.,mobile's browser can be employed through a device) and augmentingproductivity by allowing access to email communication(s) through amobile). Demonstrations and presentation by traveling salespersonworkforce, or lecturers, can also benefit from extension of mobileoperation to a device, e.g., a PC, via a reduction of salespersons orlecturers transported presentation materials, such as laptop computers.

In another aspect, reverse mobile extension can be effected, whereindevice functionality is exploited (e.g., controlled) via mobile 110. Forexample, a non-networked device can be commanded to deliver content tomobile 110. It should be appreciated that content need not be traffic;for instance, a wireless-capable camera (e.g., a ZigBee® camera) on apantry in a home can convey snapshot(s) of available items to anattached cellular phone utilized by a consumer in a grocery store inorder for the consumer to prepare a list of necessary groceries.

It should be noted that in either forward or reverse extension, mobileoperation extension interface 105 can facilitate utilization ofoperational resources on mobile 110 or on device 130.

Client component 112 automatically detects connection to clientcomponent 132 in device 130. Detection can take place according to apredetermined attachment procedure compatible with operational aspectsof device 130 and associated wired or wireless capabilities (e.g., wiredports like Ethernet or phone jack(s), universal serial bus (USB)connector(s), a RS (Recommended Standard)-232 port, or FireWire busconnector(s); or wireless ports or routers and associated antennae,e.g., WiFi gateway, Bluetooth port, infrared (IR) wireless port . . . ).Link component 115 facilitates functional coupling and informationtransport among client components 112 and 132. In an aspect, linkcomponent 115 can be a wired link; e.g., single- and multi-linetwisted-pair, such a FireWire bus; a general purpose interface bus(GPIB) line; T1/E1 phone line; a digital subscriber line (DSL) eithersynchronous or asynchronous; an asymmetric ADSL; an optical fiberbackbone; a coaxial cable . . . ). In another aspect, link component 115can be a wireless link (e.g., a line-of-sight (LOS) link or a non-LOS).It should be appreciated that link component 115 can power up device 130upon connection. To mitigate substantive mobile's battery consumption, asupplemental source of energy, e.g., a solid-state fuel cell, or athin-film solar-cell panel which can coat a portion of the surface ofthe device, can extend mobile's battery lifetime. Alternatively, or inaddition, device 130 can power mobile 110 upon attachment.

Client component 112 also manages attachment at device 130. Uponconnection, client 112 can convey credential(s) 121, e.g.,identification credentials like secure handset system identity module(SIM) information, that facilitate communication of the mobile 110identity to a wireless network (e.g., radio access network 145 andnetwork platform 150). Once credential(s) 121 are deployed (e.g., via avirtual private network, a secure socket layers, or the like) ontodevice 130, no network re-authentication of device 130 is necessary fornetworked operation. The temporary lending of SIM security informationto device 130 facilitates secure network authorization to networkentities like home location register (HLR) or Internet ProtocolMultimedia Service (IMS). In addition, such authorization, or access,mitigates duplicate registrations on HLR or IMS infrastructure; HLR orIMS can recognize secure authentication of device 130 and allow onemobile ID authorization at a time, or one authorizaiton in addition to aborrowed extension at a time.

In an aspect of the subject application, device 130 is non-networked.Thus, through the extension interface 105, device 130 exploits mobile130 wireless transport mechanism(s) as a pass-through to a wirelessnetwork (e.g., radio access network (RAN) 145 and network platform 150).Once mobile 110 disconnects either physically or logically from device130, client component 132 revokes received credential(s) 121, which caninclude license information for application(s) 124 as indicate above,and thus networked traffic no longer can be utilized. Revocation ofcredential(s) 121 substantially mitigates opportunity for networksecurity associated with the device identity to be copied or replicatedwhen device 130 is not directly connected or associated with mobile 110.

Client component 112 also can exchange traffic/content 118 (e.g., filesor application(s) data) which resides in mobile 110 with clientcomponent 132. Moreover, client 112 can convey application(s) 124 toclient component 132; the application(s) can be conveyed as asource-code package or bundle, as executable file(s), or indirectlythrough a license file, key or token once the application(s) 124 residein device 130.

With respect to wireless service, in an aspect of the subjectapplication, network platform 150 includes components, e.g., nodes,gateways, and interfaces, that facilitate packet-switched (PS) (e.g.,internet protocol (IP)) and circuit-switched (CS) traffic and controlgeneration for network wireless communication through one or moretechnologies. Radio access network 145 includes various base station andaccess points for substantially any type of coverage over-the-aircoverage with disparate spatial extents, e.g., macro (typicallyoutdoors), micro (confined outdoor spaces like parking lots, or indoorspaces such as a library, a hospital, a retail store, a residence . . .), or femto (indoor spaces) cell coverage, or any combination thereof. Asingle provider typically operates network platform 150.

Aspects of extension of mobile 110 operation to device 130, andembodiments of extension interface 105 and associated mobile 110 anddevice 130 that exploit such aspects are discussed next.

FIGS. 2A and 2B illustrate embodiments for a mobile and a device thatexploit mobile operation extension to the device, and an embodiment foran emulation component that manipulates extended mobile application(s),respectively. In block diagram 200, client component 112 can employsecurity component 212 to securely convey credential(s) 121 andapplication(s) 124. Security mechanism(s) can include at least one ofencryption, password protection, or biometric locking (e.g., informationaccess through an authorized or registered biometric instrument likefingerprint(s) or iris recognition, voice recognition, or anycombination thereof). In addition, security component 212 can securespecific traffic/content 118 that client component 112 delivers todevice 130. It is noted that security component 112 can reside at leastin part within client component 112. Memory 214 can include a credentialstorage 216, an application(s) storage 218, and content storage 220. Aprocessor 216 can provide at least in part the functionality of securitycomponent 212 and client component 112.

With respect to device 130, client component 132 receives credential(s)121, applications(s) 124, and traffic/content 118. Credential(s) 121 canbe stored in memory 240; in an aspect, credential(s) 121 can be storedin a credential(s) storage 246 (e.g., a register or a stack). Inaddition, traffic/content 118 can be utilized and generated by interfacecomponent 232, which can be accessed by an end user. It should beappreciated that interface component 232 can facilitate access to mobileextensibility (e.g., establish mobile operation extension via clientcomponent 132 within extension interface); for example, interfacecomponent 232 includes various instruments (e.g., via a keyboard, touchscreen, microphone, biometric pad, camera(s), speakers, and so forth)for data input and data output.

Device 130 can include an emulation component 234 that emulates theoperation of mobile 110, and manages synchronization component 236.Emulation component 234 can receive input data from, and convey data to,interface component 232. In addition, emulation component 234 can retainemulation operational events and records in a log records storage 242(e.g., a register or stack) and a debug records storage 244 (e.g., aregister or a stack), which can contain substantially all informationrelated to activity generated through emulation component 234 and viasynchronization component 236. In an aspect of the subject application,information stored in log records 242 and debug records 244 can beconveyed to manufacturer(s) of device 130 and mobile 110 fordevelopment, and operations and maintenance of the extension interface,emulation component 234 and synchronization component 236 as well. It isnoted that emulation component 234 can reside at least in part withinclient component 132.

It should be appreciated that disparate devices typically have disparatefunctionalities (e.g., control-oriented, image and sounddisplay-oriented, computation-oriented . . . ), and operationalresources (e.g., display size and type, computing power associated withaspects of a processor, like processor 238 resident in device 130, orgraphic processing units; memory structure and type determined at leastin part by a memory such as memory 240 present in the device; access toperipherals . . . ). Information on device functionality and operationalresources can be gleaned from identification codes or numbers likeelectronic product code(s), universal product code(s), serial number(s),etc., or from descriptor(s) or specification(s) stored in memory 240 bydevice's manufacturer or from a similar device specification resource(e.g., an online catalog, or database; not shown). In one aspect of thesubject application, emulation component 234 can migrate receivedapplication(s) 124 to device-specific application(s), which can bestored in device application(s) store 248. Through adaptation oroptimization of received application(s) 124, emulation component 234 canoptimally exploit substantially all resources available to device 130,which can result in a richer user experience.

To facilitate adaptation and optimization, application(s) 124 can becoded in a modular, object-oriented paradigm (e.g., Common LanguageInfrastructure (CLI) within a runtime system implementation (e.g.,Microsoft® Common Language Runtime (CLR), DotGNU Portable.NET, or MonoDevelopment). Modular, object-oriented coding can allow emulationcomponent 234 to reduce classes and associated metadata in receivedsource code for application(s) 124 to code assemblies containingmetadata and intermediate language that describe the source code andassociated methods that facilitate application's functionality. Suchcode reduction can be stored in log records 242 or debug records 244.Such code assemblies can be utilized to compile mobile application(s)124 received in a device (e.g., device 130) regardless of the specificsof software or firmware that operates the device. As an example,application(s) 124 can be coded employing Microsoft® C#, orsubstantially any modular, object-oriented language such as Microsoft®Visual Basic, Java™, Python, Smalltalk, C++, Verilog, Delphi, Perl,etc., can be employed as well.

With respect to FIG. 2B, the illustrated example embodiment 250 foremulation component 234 includes an optimization component 260functionally coupled to a compilation component 270; both component canaccess memory platform 280. Compilation component 270 can compilereceived application(s) 124 in a just-in-time (JIT) manner, and executeit within a runtime, or virtual machine, environment associated withemulation component 234. Optimization component 260 can analyze receivedsource-code packages or bundles to ensure application(s) 124 areobject-oriented, or component-oriented, code. Result of such analysiscan be stored in log records 242 or debug records 244. In an aspect ofthe subject application, to compile source code of application(s) 124that is optimal for a specific device (e.g., device 130), compilationcomponent 270 can exploit optimization component 310 to adapt receivedapplication source code through code elements stored in modules store282, objects store 284, procedures store 288, classes store 286 and/ormetadata store 290. Adaptation or optimization can include incorporationof at least one of modules, objects, classes, procedures or metadata inorder to achieve an optimal performance for the specific device (e.g.,device 130), and inclusion of metadata that manipulates a set ofassemblies associated with application(s) 124 source code in accordancewith features (e.g., aspects of operational resources) provided bydevice 130, and characteristics of application(s) 124. Records ofadaptation or optimization, or both, can be stored in log records 242 ordebug records 244. It should be appreciated that in view of the modularcharacteristics of the optimal code, substantially any module, object,procedure, class, or metadata generated as a result of optimization canbe stored within memory platform 330 in a corresponding storage element.It should be further appreciated that compilation component 270 andoptimization component 260 can be employed in development or design ofapplication(s) 124, so as to facilitate code structures (e.g.,object(s), class(es), procedure(s), . . . ) to memory platform 280 thatare necessary to achieve specific customization.

To automatically adapt or manipulate received application(s) 124,optimization component 260 can employ artificial intelligence. Asindicated above, the term “intelligence” refers to the ability to reasonor draw conclusions about, e.g., infer, the current or future state of asystem based on available information about the system. Artificialintelligence (AI) can be utilized to identify a specific context oraction, or generate a probability distribution of specific states of asystem without human intervention. To infer optimal source code toachieve optimal performance of a received application within a device(e.g., device 130), optimization component 310 can rely on artificialintelligence techniques, which apply advanced mathematicalalgorithms—e.g., decision trees, neural networks, regression analysis,principal component analysis (PCA) for feature and pattern extraction,cluster analysis, genetic algorithm, and reinforced learning—toinformation on application's code source structure.

In particular, optimization component 310 can employ at least one ofvarious methodologies for learning from data and then drawing inferencesfrom the models so constructed, e.g., Hidden Markov Models (HMMs) andrelated prototypical dependency models, more general probabilisticgraphical models, such as Dempster-Shafer networks and Bayesiannetworks, e.g., created by structure search using a Bayesian model scoreor approximation, linear classifiers, such as support vector machines(SVMs), non-linear classifiers, such as methods referred to as “neuralnetwork” methodologies, fuzzy logic methodologies, and other approachesthat perform data fusion, etc.) in accordance with implementing variousautomated aspects described herein. The foregoing methods can be appliedto identify application's source code structure (e.g., objects, classes,or metadata employed for specific functionality) and associatedrelationships, and suitable modifications (e.g., overload specificclasses, change class inheritance or object types, change logic ofspecific procedures or exploit optimized libraries) that can result inoptimal performance or utilization of available resources to a device(e.g., device 130).

FIG. 3 is a block diagram 300 of example embodiments of a mobile 310 anda device 330 to which mobile operation has been extended via anextension interface 105. In mobile 310, components with like numerals asthose in mobile 110 have substantially the same functionality thereof.Mobile 310 is functionally connected to device 330 via an extensioninterface 105 as described above in connection with FIG. 1, for example:Extension interface 105 includes client component 112, which can residein mobile 310 and is linked through link 115 to client component 132within device 330. In embodiment 310, upon detection of connectivity todevice 130, client component 112 conveys credential(s) that are storedin credential(s) storage 246. In addition, a plug-and-play (P&P)component 312, functionally coupled to client component 112, scans fordriver(s) 316 via driver scanner, or driver scanner component, 314. Itis noted that P&P component 312 can also reside within client component112. In an aspect, driver(s) 316 can be retrieved upon a request fromclient component 112 in response to detection of mobile operationextension to device 330, and utilized to facilitate communication oftraffic or content (e.g., traffic/content 124) thereto. In an aspect ofthe subject application, driver(s) 316 can be downloaded from theInternet (e.g., ISP network 170 via network platform 150; driver(s) 316content can be received through random access network 145 throughwireless downlink 137 _(DL)). Retrieved driver(s) 316 can be temporarilystored in memory 318, or persisted (e.g., stored for an undeterminedtime interval) in driver storage 320 as a part of a driver library forfuture utilization of device 330. In another aspect, mobile 310 caninfer through AI which drivers to retain in driver storage 320 based onhistoric data on mobile extension usage (e.g., devices to which mobileis frequently extended). Such automated discrimination can save awireless network that server the mobile RF bandwidth and time at theexpense of memory utilization; it should be appreciated that memory(e.g., memory 318) is a resource substantially more affordable than RFbandwidth, which is typically regulated.

In addition, it should be appreciated that device 330 can receivetraffic or content that can be conveyed to an end user via interfacecomponent 232. Moreover, client component 132 can manage interactionwith an end user via the interface component 232. Information associatedwith such interaction can be conveyed to, and utilized by, mobile 310.

At least two advantages of exploiting plug-and-play component 312 as apart of extension interface for mobile operation extension are thefollowing. (i) Devices with low-level computing resources (e.g.,cameras, data projectors . . . ) can be utilized to deliver mobiletraffic or content stored within mobile 310 without a need to emulatemobile operation. For example, mobile device 330 can be a multimediaprojector that can deliver mobile traffic, e.g., sound or voice, viaextension interface 105; lectures, presentations, television shows, andso on, can be broadcasted through the multimedia projector via mobile310. In particular, a lecturer or presenter can arrive at a lecture hallor presentation site, connect his or her mobile to the multimediaprojector via an extension interface 105, download suitable drivers,retrieve his or her presentation from a server in-the-cloud resident ina wireless network platform (e.g., network platform 150) or associatednetworks, and proceed to deliver his or her lecture or presentation.(ii) In view of client component 112 exploits received driver(s) 316 orstored driver(s) in driver storage 320, substantially any device 330(e.g., contemporary devices, or legacy devices) can be extended toconsume mobile content or traffic.

FIG. 4 illustrates a block diagram of an example system 400 that scansfor available wireless devices to extend mobile operation thereto. Insystem 400, extension interface comprises client component 112 and itscounterpart resident in each of a set of devices 430 ₁-430 _(M) (M is apositive integer) that can deliver wireless signal. Additionally, linkcomponent 115 is embodied in a wireless downlink 425 _(DL) and uplink425 _(UL), the links operate in accordance with wireless technologyemployed by a specific device that partakes in establishing such links,which can be facilitated through a multi-mode operation of mobile 510.In an aspect of example system 410, client component 112 exploitsscanner component 412 to scan one a set of wireless channels that mobile410 can utilize for communication for signals transmitted from a set ofdevices 430 ₁-430 _(M). Substantially any of devices 430 ₁-430 _(M) canoperate and provide functionality in its native mode (e.g., tetheredquasi-stationary operation), and send wireless pilot signal(s) ormanagement frames at specific time instants in order to facilitatedetection by a mobile (e.g., mobile 410). The periods at which pilotsignal or management frames are conveyed can be determined by a clientcomponent that is part of the extension interface and resides within thedevice. In an aspect, as indicated above, mobile device can be amulti-mode wireless device and thus various wireless signals (e.g.,signaling pilot in control channel(s), or in-band signaling such asmanagement frames) in various RF bands and modulated in accordance withmultiple modulation schemes can be probed. Scanner component 412 canreport available wireless signal(s) to client component 112 via reportcomponent 414. Report component 414 can provide such report(s) to an enduser of mobile 410 through multiple indicia (e.g., visual or audiosignaling). It is noted that scanner component 412 and report component414 can be part of the extension interface or reside within clientcomponent 112.

Reports generated via report component 414 are actionable informationthat can be employed to determine whether to automatically or on-demandextend mobile operation to a detected, available wireless device (e.g.,device 430 ₂). As an example, an extension interface in a subscriberstation (e.g., mobile 410) can scan and detect a security camera (e.g.,device 430 ₂) with wireless capability (e.g., a device based on ZigBee®wireless communication technology, or substantially any other wirelesstechnology), so that images captured by the security camera can bedisplayed through the subscriber station. (The latter is an example ofreverse mobile extension.) In a scenario, a business owner can arrive athis or her store and notice suspicious, unexpected activity or events(e.g., lights on, semi-open door, window broken . . . ) inside or nearthe store, and thus utilize his or her mobile to extend mobileoperation, and manipulate or operate the security camera wirelessly toconfirm it is safe to enter the store. It should also be appreciatedthat substantially any information (e.g., images of individuals whobroke into the store) received from the security camera, which has beenextended to operate through the mobile, can be manipulated (e.g., apicture taken, images relayed to law enforcement officials, and so on)via the mobile.

In an aspect of mobile 410, processor 416 provides at least in part thefunctionality of client component 112, scanner component 412, and reportcomponent 414. Data structures, code instructions, and algorithmsrelated to such functionality can be stored in memory 418 and utilizedby processor 416.

FIG. 5 is a block diagram of an example system 500 that exploitsdisparate networks upon extension of mobile operation to a device.Mobile 510 can communicate wirelessly through a first network platform A530 access via a first RAN A 535; link 537 conveys traffic and signalingamong network platform A 530 and RAN A 535, and link 539 deliverstraffic or signaling among mobile 510 and RAN A 535. As discussed above,telecommunication and service can be extended from mobile 510 to device520 through an extension interface 105 that comprises a client component112 that resides within mobile 520 and is linked, through link component115, to a client component 132 in device 520. In system 500, a scannercomponent 412 can detect signal(s) in disparate RF channels and variousmodulation formats, and attach to a second RAN that conveys suchsignal(s). Scanner component 412 can reside at least in part withinclient component 112. Handover component 514 can manage handoff to thesecond network. In an aspect, handover component 514 can include varioushandoff procedures (e.g., Location Area Update procedure) in order toattach to disparate wireless networks. Mobile 510 can handover to asecond RAN B 545 managed by a second network platform B 540; links 549and 547 communicate data and control among mobile 510 and RAN B 545, andnetwork platform B 540 and RAN B 545. In an aspect, the second wirelessnetwork can boost service coverage and improve bandwidth utilization inthe first network, with ensuing improved operation of both mobile 510and device 520. It should be appreciated that RAN A 535 and RAN B 545can utilize disparate RF bands, either licensed or unlicensed, andutilized disparate telecommunication technology; for example, RAN A 535can utilize 3GPP LTE technology while RAN B 545 can exploit WiFi orfemto cell technology.

In an aspect of system 500, a processor (not shown) can provide at leastin part the functionality of substantially any component within mobile510, while a memory (not shown) can retain data structures, codeinstructions, and algorithms related to such functionality; suchcontents can be utilized by the processor.

FIG. 6 is a block diagram of an example system 600 that exploits amobile operation extension interface 105 to relay communication(s) amongmultiple parties. Mobile 610 extends mobile operation to device 620 viaan extension interface 105 that, as discussed above, can comprise aclient component 112 that resides in mobile 610 and a client component132 within device 620, the client components 112 and 132 mutually andfunctionally connected through link component 115. Subscriber station640 (e.g., a portable personal computer) can exploit wireless links 647_(UL) and 647 _(DL) to communicate via RAN 145 with network platform 150and establish a telecommunication with mobile 610. In addition, mobilestation 650 can also establish a communication with mobile 610 and joina voice or data session underway among subscriber station 640 and mobile610. Mobile station 650 communicates through RAN 145, via wireless links657 _(UL) and 657 _(DL), with network platform 150, which can administerat least in part communication with mobile 610.

Within example system 600, each party in a multi-party call (e.g., avoice session or data session) can exploit substantially all resourcesavailable to the user equipment utilized for communication. For example,a videoconference can be established: Mobile station 640 can exploit awebcam to convey images in addition to sound. Likewise, mobile station650 can utilize a built-in camera to send images in addition to sound.Moreover, mobile 610 can extend mobile operation to device 620 via anextension interface 105 in accordance with aspects of the subjectapplication, and exploit audiovisual resources associated with device620 (e.g., a personal computer). Once mobile operation has been extendedto device 630, mobile 610 can serve as a pass-through element, and relaytraffic to device 620. In an aspect, client component 112 manages oroperates a scheduler component 612 that schedules traffic to device 620in accordance to specific quality of service (e.g., traffic handlingpriority, guaranteed bitrate, minimum bitrate, minimum tolerablelatency, maximum bit error or packet loss rate . . . ) associated withsubscriber station 640 or mobile station 650. Scheduler component 612can utilize substantially any scheduling techniques such as round robin,or proportionally fair. To facilitate scheduler component 612 operation,three-way communication among mobile 610, subscriber station 640 andmobile station 650 can be implemented within a multiple-inputmultiple-output (MIMO) mode of operation. A serving base station withinRAN 145 can schedule disparate antenna subsets within mobile 610 fortraffic and control communication to and from subscriber station 640 andmobile station 650. It is noted that scheduler component 612 can resideat least in part within client component 112.

With respect to device 620, client component 132 can process and routeinformation carried by data packets received from mobile 610 to adisplay interface 630, which can render visual or aural indicia todeliver the received information to an end user. For instance, displayinterface 630 can (i) broadcast images associated with subscriberstation 640 (e.g., image 1 632 ₁) or mobile station 650 (e.g., image 2632 ₂), such as images of a lecture hall, conference room, outdoor camp,etc., wherein the received data originates; (ii) display textualinformation associated with traffic conveyed by subscriber station 640(e.g., text 1 634 ₁) or mobile station 650 (e.g., text 2 634 ₂), thetextual information can be presented in accordance with variousgestures, like sideways scrolling text, scroll-down text, staticrendering of text, etc.; and (iii) deliver sound associated withsubscriber station 640 (e.g., audio 1 636 ₁) or mobile station 650(e.g., audio 2 636 ₂). It is to be noted that displayed information andindicia associated thereof can vary based at least in part on thecontent to be displayed and the nature of the call. In addition, a dataentry interface 622 can facilitate generation of data to be conveyed,via client component 132, to mobile 610 to be then relayed to eithersubscriber station 640 or mobile station 650.

In an aspect, data packets received from mobile 610 can be processed byadd-on component 624 prior to delivery to an end user through displayinterface 630. It is noted that the add-component 624 can reside atleast in part within client component 132 even though it is illustratedas external thereto. Data generated via data entry interface 622 can beprocessed prior to communication to mobile 610 via client component 132for further communication to subscriber station 640 or mobile station650. For example, add-on component 624 can translate received text orvoice so as to deliver information in a suitable language for an enduser of device 630 or subscriber that operate subscriber station 640 ormobile station 650. Additionally, add-on component 624 can generate agraphical rendition (e.g., imagery abstraction, or sign language) of thereceived text or voice to facilitate comprehension of conveyedinformation. In an aspect, AI or machine learning techniques can beemployed to generate such a graphical rendition. As another example,add-on component 624 can convert text to voice, or vice versa, in orderto mitigate possible aural impairment(s) of end user of device 630.

In another aspect of the subject application, to ease bandwidth andmitigate latency issues that may arise as a result of a rich trafficcommunication among the parties of the three-way call (e.g., a voicesession or data session), an offloading network (e.g., RAN B 545 andnetwork platform B 540; not shown in FIG. 6) can be employed totransport traffic to and from one of mobile station 650 or subscriberstation 640. In another aspect, telecommunication among multiple partiescan also be established, and example system 600 can be exploited forcommunication among more than three wireless devices. In an alternativeor additional scenario, a wired device that utilizes a landline fortelecommunication can utilize a wire link to connect to a telephonynetwork (e.g., telephony network(s) 160) to participate in a multi-partycommunication in example system 600.

It should be appreciated that mobile 610 can include substantially anycomponent comprised in embodiments 310, 410, and 510 for a mobile, andexploit substantially all associated functionality of such components.As an example, mobile 610 can include plug-and-play component 312, whichcan facilitate multi-party communication (e.g., a videoconference,consultation with a customer service representative . . . ) inaccordance with aspects described above through utilization ofsubstantially any device with a display interface and a data entryinterface 622, like an airport internet kiosk.

Additionally, processor 614 can provide at least in part thefunctionality of substantially any component within mobile 610, whilememory 616 can retain data structures, code instructions, and algorithmsrelated to such functionality; such contents can be utilized byprocessor 614. Increased complexity of multi-way communication can bemanaged by multi-processor computing platform within mobile 610. Withrespect to device 620, a processor (not shown) and a memory (not shown)can provide at least a portion of the functionality of substantially allcomponents within device 620.

In view of the example systems described above, example methodologiesthat can be implemented in accordance with the disclosed subject mattercan be better appreciated with reference to flowcharts in FIGS. 7-14.For purposes of simplicity of explanation example methodologies, ormethods, are presented and described as a series of acts; however, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, those skilled in the art will understand andappreciate that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram, orinteraction diagram. Moreover, not all illustrated acts may be requiredto implement a methodology in accordance with the subject specification.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers for execution by aprocessor or for storage in a memory.

FIG. 7 is a flowchart of an example method 700 for extending mobilehandset operation to a device according to aspects described in thesubject specification. At act 710, a mobile handset is attached to adevice through an extension interface (e.g., extension interface 105).In an aspect, the extension interface can include a client componentresiding in the mobile handset, a client component residing in thedevice, and a link component that connects both client components. Thedevice is typically an electronic device with a set of functionalities.Attachment can proceed according to device-specific protocol(s), suchprotocols can be stored in a memory in the mobile handset. Attachmentprotocol(s) can be based at least in part on a handshake procedureincluding at three-step mechanism: Acknowledge-Request-Grant, whereinconnectivity is acknowledged by the mobile handset and device, a requestto attach is set forth by the mobile handset, and the attachment isgranted by the device. Acknowledgement step can include recognition ofthe device, e.g., through collection of a serial number or product codethat identifies the device, and download of device-specific attachmentinstructions from a network, e.g., ISP network(s). Moreover,acknowledgement can include powering-up the device. To facilitateattachment, device manufactures can provide attachment protocols tonetwork operator(s).

At act 720, mobile handset's security credentials (e.g., SIM contents)are conveyed to the attached device. Such security credentials canenable a mobile service provider to recognize the device as part of aserving wireless network. In an aspect, security credentials areconferred to the device for a finite time interval, which typically isthe time span during which the mobile handset and device are attached.At act 730, an application (internet protocol (IP) television client,video- and sound-streaming client . . . ) and content (e.g., files,passwords) associated with the mobile handset are conveyed to theattached device. It is noted that the application and content associatedwith the mobile handset can reside within the mobile or it can be storedin an in-the-cloud server (e.g., a server within network platform 150,ISP network 170, LAN 180) to which the mobile has access. In an aspect,the application is conveyed as a source-code bundle for the attached togenerate a suitable executable application.

At act 740, traffic from a wireless network to the attached device, andfrom the attached device to the wireless network, is relayed. The mobilehandset serves are pass-through relay.

FIG. 8 displays a flowchart of an example method 800 for conveyingcontent to a device attached to a mobile handset through an extensioninterface according to aspects described in the subject application. Atact 810, a mobile handset is attached to a device through an extensioninterface. It is to be noted this act is substantially the same as act710 in example method 700. At act 820, drivers to operate the device arescanned for and downloaded when encountered. A wireless network thatprovides mobile service can facilitate access to a wide-area network(e.g., ISP network 170) to scan, or search, for the drivers and retrievethem when suitable for device operation. In an aspect, a plug-and-playcomponent within the mobile handset can conduct the scanning anddownloading. At act 830, content and traffic are conveyed to the devicebased at least in part on the downloaded drivers.

FIG. 9 is a flowchart of an example method 900 for extending mobileoperation to available devices with wireless capability according toaspects disclosed herein. At act 910, an environment is scanned fordevices capable of wireless operation. It is noted that the devices cangenerally effect their functionality without reliance on wirelessoperation, with wireless operation enabled for predetermined purposes orwithin an on-demand basis. In an aspect, the environment can be aconfined area (e.g., a building, or a building and a portion of anoutdoor area). A mobile handset performs the scans. At act 920,identified devices are reported. Such reporting can be effected througha reporting component within the mobile handset. At act 930, anidentified device is selected and mobile operation is extended to theselected device. In an aspect, extension of mobile operation can beimplemented through one or more acts of example method 700.

FIG. 10 displays a flowchart of an example method 1000 for utilizing analternative or offloading network for extension of mobile operation to adevice. At act 1010, mobile operation is extended to a device. Thedevice is typically an electronic device with a set of specific enabledor capable functionalities. In an aspect, extension of mobile operationcan be implemented through one or more acts of example method 700. Atact 1020, an environment is scanned for wireless network(s) that servesa confined area within the environment and that encompasses the device.In another aspect, service through such a network can be receivedthrough local access points, or HNBs. At act 1030, mobile operation ishanded-over to a wireless network identified via the scan. It should beappreciated that such handover can at least boost quality of service toa mobile handset that extends mobile operation to the device, andoffload a serving network. A handover component can implement hand-offaccording to a procedure compatible with the wireless technologyutilized by the identified wireless network. At act 1040, traffic isrelayed to the device through the identified wireless network to whichmobile operation is handed-off.

FIG. 11 presents a flowchart of an example method 1100 for exploitingextension of mobile operation of a device to conduct a multi-part callaccording to aspects disclosed herein. Call can include a data sessionor a voice session. At act 1110, a mobile handset is attached to adevice through an extension interface. At act 1120, mobile handset'ssecurity credentials are conveyed to the attached device. It is notedthat acts 1110 and 1120 are substantially the same as acts 710 and 720,respectively, in example method 700. At act 1130, call(s) is establishedwith a set of telecommunication devices, which can include wireless andwired devices, via one of the attached device. Call can be initiated byutilizing a component that emulates handset operation (e.g., emulationcomponent 234). In an alternative or additional aspect, a call can beestablished through the mobile handset through which mobile operation isextended to the device. At act 1140, traffic from the set oftelecommunication devices to the attached device is scheduled. Suchscheduling can be based on predetermined QoS parameters associated withoperation and traffic of one or more of the telecommunication devices inthe set of devices. Additionally, control information conveyed through arandom access networks that sustains communication with the mobilehandset can be employed for scheduling traffic. At act 1150, traffic isrelayed from the attached device to the set of telecommunicationdevices, and vice versa.

FIG. 12 is a flowchart of an example method 1200 for exploiting mobileservice through a mobile handset extension interface according toaspects described in the subject specification. At act 1210, a device isattached to a mobile handset through an extension interface. In anaspect, the device is a non-networked electronic device that implementsits one or more functionalities through a set of components to which aprocessor, assisted through a memory component(s), confers at least partof the device's components functionalities. At act 1220, mobilehandset's security credentials are received and retained. In an aspect,the security credentials form a set of one or more entities. Suchcredentials are retained for a finite time span that expires whenextension interface no longer provides mobile operation (e.g., logiccondition of interface is set to non-operational). At act 1230, mobilehandset operation is emulated; for example, and emulation componentwithin the attached device can facilitate substantially all operationalfeatures of the mobile handset. At 1240, traffic is received from themobile handset; the traffic is provided through a wireless network thatserves the mobile. At act 1250, application(s) and content are receivedfrom the mobile handset. Application(s) can be received as a source-codepackage that the device can manipulate to generate a device-specificapplication that emulates the application on the mobile handset. At act1260, content generated through emulation is synchronized with themobile handset, thus updated content remains in the attached mobilehandset. At act 1270, traffic generated at the device, which can be apart of emulation of the mobile handset, can be delivered through theextension interface. Traffic is typically delivered to a party thatmaintains a call with the mobile handset, the call effected through thedevice. It should be appreciated that maintaining a call through thedevice allows a subscriber to exploit substantially all the operationalresources of the device (e.g., substantive display real estate, soundand video capabilities, computing strength, and so on).

FIG. 13 is a flowchart of an example methodology 1300 for generating andemploying a device-specific application from a mobile-specificapplication when mobile operation is extended to the device according toaspects of the subject application. At act 1310, source code for anapplication received through a mobile operation extension interface isoptimized and compiled. It should be appreciated that act 1310 generatesa device-specific application. In an aspect, source code can beobject-oriented, and optimization can include modification of structures(e.g., modules, objects, classes, and metadata) associated with thereceived source code. At act 1320, the optimized executable applicationthat results at least in part from optimization and compilation of thereceived source code is retained. At act 1330, the optimized applicationis utilized. At act 1340, log and debug records of utilization of theoptimized application are retained. It is noted that log and debugrecords associated with application optimization and compilation canalso be stored.

FIG. 14 is a flowchart of an example methodology 1400 for manipulatingand delivering traffic through a mobile operation extension interfaceaccording to aspects of the subject application. In an aspect, a device(e.g., device 620) can implement example methodology 1400. At act 1410,traffic is received from a set of telecommunication devices through amobile operation interface. The mobile operation interface functionallyconnects a mobile handset to the device, through a link component and atleast two client components, one that resides in the mobile handset(e.g., mobile 110) and another that resides in the device.

At act 1420, the received traffic is processed according to a set ofadd-on features. An add-on component (e.g., add-on component 624) canprovide one or more of the add-on features; e.g., translation,voice-to-text and text-to-voice conversion, voice recognition andassociation of specific, customized add-on features like uploading aparticular address-book for an end user whom his or her voice has beenrecognized, etc. At act 1430, the processed traffic is delivered. An enduser typically receives the traffic through a display interface, whichcan convey the traffic via various gestures (e.g., visual, aural,tactile like touch-based actuation . . . ) to an end user of the device.

At act 1440, traffic or data is generated in response to the delivered,previously processed traffic. Generation of data can be assisted througha data entry interface (e.g., data entry interface 624). Data generationcan be (a) explicit or (b) implicit. In the former case, an end userconveys the information or content to be delivered, the content can beprocessed prior to delivery via the extension interface. In (b), presetinformation can be delivered when an end-user interacts in predeterminedmanners with the data entry interface (e.g., preset touch keys), or whenthe device that generates and conveys the traffic infers thatpredetermined information is to be communicated. For example, in case analarm or substantially any sound(s) that can be assessed (e.g., via anintelligence component utilizing AI techniques) to be an indicator ofend-user distress. As another example, when generated, or collected,images convey an emergency situation, a distress call can be conveyedimplicitly. In particular, a bank employee can extend mobile operationto a closed-circuit camera at a time of a robbery, and an ensuingdistress call can be generated and conveyed without explicit, andpotentially fatal, interaction of the bank employee with his or hermobile handset.

To provide further context for various aspects of the subjectspecification, FIG. 15 illustrates a block diagram of an exampleembodiment 1500 of a mobile 1510 that can be attached to a device (e.g.,device 130) to extend mobile operation through an extension interface(e.g., extension interface 105) in accordance with aspects describedherein. Additionally, FIG. 16 presents a block diagram of a device towhich mobile operation can be extended in accordance with aspectsdescribed herein.

In mobile 1510, which can be a multimode access terminal, a set ofantennas 1569 ₁-1569 _(N) (N is a positive integer) can receive andtransmit signal(s) from and to wireless devices like access points,access terminals, wireless ports and routers, and so forth, that operatein a radio access network, e.g., RAN 145. It should be appreciated thatwhile antennas 1569 ₁-1569 _(N) are a part of communication platform1525, which comprises electronic components and associated circuitrythat provide for processing and manipulation of received signal(s) andsignal(s) to be transmitted. In an aspect, communication platform 1525includes a receiver/transmitter 1566 that can convert signal from analogto digital upon reception, and from digital to analog upon transmission.In addition, receiver/transmitter 1566 can divide a single data streaminto multiple, parallel data streams, or perform the reciprocaloperation; such operations typically conducted in various multiplexingschemes. Functionally coupled to receiver/transmitter 1566 is amultiplexer/demultiplexer (mux/demux) component 1567 that facilitatesmanipulation of signal in time and frequency space. Electronic mux/demuxcomponent 1567 can multiplex information (data/traffic andcontrol/signaling) according to various multiplexing schemes such astime division multiplexing (TDM), frequency division multiplexing (FDM),orthogonal frequency division multiplexing (OFDM), code divisionmultiplexing (CDM), space division multiplexing (SDM). In addition,mux/demux component 1567 can scramble and spread information (e.g.,codes) according to substantially any code; e.g., Hadamard-Walsh codes,Baker codes, Kasami codes, polyphase codes, and so on. Amodulator/demodulator (mod/demod) component 1568 is also a part ofcommunication platform 1525, and can modulate information according tovarious modulation techniques, such as frequency modulation (e.g.,frequency-shift keying), amplitude modulation (e.g., M-ary quadratureamplitude modulation (QAM), with M a positive integer; amplitude-shiftkeying (ASK)), phase-shift keying (PSK), and the like. In an aspect ofembodiment 1500, mod/demod component 1568 is functionally coupled tomux/demux component 1567.

In embodiment 1500, multimode operation chipset(s) 1515 allows mobile1510 to operate in multiple communication modes in accordance withdisparate technical specification for wireless technologies. In anaspect, multimode operation chipset(s) 1515 utilizes communicationplatform 1525 in accordance with a specific mode of operation. Inanother aspect, multimode operation chipset(s) 1515 can be scheduled tooperate concurrently (e.g., when N>1) in various modes or within amultitask paradigm.

Extension interface 1518 facilitates extension of mobile operation to adevice (e.g., device 130) in accordance to aspects described in thesubject specification. Extension interface 1518 can include a clientcomponent (e.g., client component 112) and at least a portion of a link(e.g., link component 115) that can provide, at least in part, bothlogical (e.g., functional) and physical attachment to the device.

Mobile 1510 also includes a processor 1535 configured to conferfunctionality, at least in part, to substantially any electroniccomponent within mobile 1510, in accordance with aspects of the subjectapplication. As an example, processor 1535 can be configured to execute,at least in part, instructions in multimode operation chipset(s) thatafford multimode communication through mobile 1510 like concurrent ormultitask operation of two or more chipset(s). As another example,processor 1535 can facilitate mobile 1510 to receive traffic (e.g.,various data flows) through extension interface 1518, and relay suchtraffic via communication platform 1525. As yet another example,processor 1535 can receive synchronization indications via extensioninterface 1518 to maintain content synchronized with operation performedin a device (not shown) attached to mobile 1510 via extension interface1518. A link dock 1519 can be operationally coupled to extensioninterface 1519 to facilitate attachment of link component(s) that are atleast a part of extension interface 1519. It should be appreciated thatprocessor 1535 can store (e.g., in cache memory) at least temporarilytraffic received from either extension interface 1518 or communicationplatform 1525, or both. Moreover, processor 1535 facilitates mobile 1510to process data (e.g., symbols, bits, or chips) formultiplexing/demultiplexing, modulation/demodulation, such asimplementing direct and inverse fast Fourier transforms, selection ofmodulation rates, selection of data packet formats, inter-packet times,etc. Memory 1555 can store data structures (e.g., metadata); codestructure(s) (e.g., modules, objects, classes, procedures) orinstructions; network or device information like policies andspecifications, attachment protocols; code sequences for scrambling,spreading and pilot (e.g., reference signal(s)) transmission; frequencyoffsets, LACs or substantially any other cell IDs, and so on.

In embodiment 1500, processor 1535 is functionally coupled (e.g.,through a memory bus) to memory 1555 in order to store and retrieveinformation necessary to operate and/or confer functionality, at leastin part, to communication platform 1525, multimode operation chipset(s)1515, extension interface 1518, and other operational aspects ofmultimode user equipment 1510.

FIG. 16 presents a block diagram of an example embodiment 1600 of adevice that can operate in accordance with aspects described herein.Device 1605 includes a functional platform 1610 that comprises a set ofcomponents that provide at least in part specific functionality of thedevice in accordance with at least one device aspect described herein.Additionally, device 1605 includes an extension interface 1615 inaccordance with aspects described herein. A link dock 1614 canfacilitate to link (e.g., through a link component 115) device 1605 to amobile handset (not shown) attached thereto through the extensioninterface 1615. Link dock 1614 can include jacks for various connectorsof various types: Ethernet, USB, GPIB, RS-232, FireWire, optical, and soforth.

Moreover, device 1605 can include in an aspect a communication platform1655 that can provide wireless communication capabilities in addition toconnectivity of device 1605 through wired links (e.g., Ethernetconnection to server(s); not shown). With respect to wirelesscapability, communication platform 1655 includes substantially the samecomponent and associated functionality as communication platform 1525 inmobile 1510. Communication platform 1655 is functionally connected to aset of K antennas 1657 ₁-1657 _(K), (K is a positive integer) that canprovide MIMO communication.

A peripheral component 1625 can include, or facilitate connection to,additional devices such as printer(s), media player(s), wirelessrouter(s), biometrics touch-pad(s), etc. In an aspect, peripheralcomponent can be functionally coupled to extension interface 1615 andthus mobile operation can also be extended to peripheral devices (e.g.,traffic associated with a videoconference can be recorded in a DVD(Digital Versatile Disc) recorder which can be a peripheral deviceconnected to device 1605.

Additionally, the display interface 1635 can be a part of functionalplatform 1610 (e.g., when device 1605 is a PC, a television, abackprojector component, a data projector . . . ), and it can alsodisplay functions that control functionality of device 1605, or revealoperation conditions thereof (e.g., light-emitting-diode (LED)indicator(s) of mobile operation attachment). For example, displayinterface 1635 can display at least one of a graphical user interface toexploit emulation of mobile handset operation in device 1605, or trafficor content received from a mobile handset attached to the device throughextension interface. In an aspect, display interface 1635 can be aliquid crystal display (LCD), a plasma panel, a monolithic thin-filmbased electrochromic display, and so on.

It should be appreciated that device 1605 can include a data entryinterface that can allow an end user to command device 1605 viaconfiguration of functional platform 1610, interact with an attachedmobile handset (not shown) through device 1605, and generate dataassociated with communication through an attached mobile handset.

Power supply 1675 can power-up device 1605 and substantially anycomponent included thereon. It should be appreciated that alternative oradditional embodiments 1600 may not include power supply 1675 and bepowered via an attachment link associated with extension interface 1615.

Device 1605 also includes memory 1690 functionally coupled to processor1685, and can store data structures, codes structures and instructions,and substantially any type of software or firmware that processor 1685can execute to provide functionality associated with functional platform1610.

Various aspects or features described herein may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In particular, the aspects or featurescan be implemented through program modules stored in a memory andexecuted by a processor, and/or other combination of hardware andsoftware, e.g., firmware. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ).

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” and substantially any other information storage componentrelevant to operation and functionality of a component, refer to “memorycomponents,” or entities embodied in a “memory” or components comprisingthe memory. For example, information relevant to operation of variouscomponents described in the disclosed subject matter, and that can bestored in a memory, can comprise, but is not limited to comprising,subscriber information; femto cell configuration (e.g., devices servedby a femto AP; access control lists, or white lists) or service policiesand specifications; privacy policies; add-on features, geographicallocation tolerances, and so forth. It will be appreciated that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of systems and methodsthat provide advantages of the subject application. It is, of course,not possible to describe every conceivable combination of components ormethodologies for purposes of describing the subject application, butone of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A device, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: sendinginstruction data representing an instruction that facilitates a returnof content data to the device from a remote device by facilitating anemulation of a function associated with the device by the remote device;determining that a logical termination of a connection establishedbetween the device and the remote device has been initiated; receivingrevocation command data from the remote device; and as a function of therevocation command data, revoking a security credential sent to theremote device as security data.
 2. The device of claim 1, wherein theemulation of the function associated with the device comprisessynchronizing content generated by and associated with the remotedevice.
 3. The device of claim 1, wherein the operations furthercomprise forwarding first traffic, received from a radio access networkdevice, to the remote device.
 4. The device of claim 3, wherein theoperations further comprise forwarding second traffic, received from theremote device, to the radio access network device.
 5. The device ofclaim 1, wherein the security credential comprises a license tofacilitate the emulation of the function by the remote device.
 6. Thedevice of claim 1, wherein the operations further comprise performing asearch of a radio access network device for a driver to facilitate theemulation of the function by the remote device.
 7. The device of claim1, wherein the operations further comprise downloading a driver from aradio access network device to facilitate the emulation of the functionby the remote device.
 8. The device of claim 1, wherein the operationsfurther comprise, in response to downloading, as a function of a remotedevice type, a driver from a radio access network device to facilitatethe emulation of the function by the remote device, storing the driverto a storage device.
 9. The device of claim 1, wherein the operationsfurther comprise, in response to downloading a driver from a radioaccess network device and as a function of the security credential,forwarding the driver to the remote device.
 10. The device of claim 1,wherein the operations further comprise, prior to sending the securitycredential to the remote device, using a voice recognition lockingprocess to secure the security credential based on voice informationrepresentative of a voice.
 11. The device of claim 1, wherein theoperations further comprise, prior to sending the security credential tothe remote device, using an iris recognition locking process to securethe security credential based on iris information representative of aniris.
 12. A non-transitory computer readable storage medium comprisingexecutable instructions that, in response to execution, cause a systemcomprising a processor to perform operations, comprising: in response toreceiving instruction data representing an instruction from a mobiledevice, emulating a function associated with the mobile device to returncontent to the mobile device; initiating a logical termination of aconnection established with the mobile device; and facilitating arevocation of a security credential associated with the connection bythe mobile device.
 13. The non-transitory computer readable storagemedium of claim 12, wherein the operations further comprise sendingcontent to the mobile device as a function of the instruction.
 14. Thenon-transitory computer readable storage medium of claim 12, wherein theoperations further comprise receiving first traffic from the mobiledevice, and wherein the first traffic was obtained by the mobile devicefrom a radio access network device.
 15. The non-transitory computerreadable storage medium of claim 12, wherein the operations furthercomprise sending second traffic to the mobile device to be forwarded toa radio access network device.
 16. The non-transitory computer readablestorage medium of claim 12, wherein the operations further comprisereceiving a driver from the mobile device, and wherein the driverfacilitates the emulating the function associated with the mobiledevice.
 17. A method, comprising: initiating, by a system comprising aprocessor, a return of content data to the system from a remote deviceby facilitating a function associated with a mobile device beingemulated by the remote device; determining, by the system, that alogical termination of a connection established between the mobiledevice and the remote device has been initiated; and in response toreceiving from the remote device revocation command data representing arevocation command, revoking, by the system, a security credentialpreviously sent to the remote device.
 18. The method of claim 17,further comprising forwarding, by the system, traffic received from aradio access network device to the remote device as a function of thesecurity credential.
 19. The method of claim 17, further comprisingforwarding, by the system, traffic received from the remote device to aradio access network device as a function of the security credential.20. The method of claim 17, further comprising: downloading a driverfrom a radio network access device; and forwarding the driver to theremote device, wherein the driver facilitates the function associatedwith the mobile device being emulated by the remote device.